ci: use reusable workflows from pyTooling/Actions #31
Conversation
umarcor
force-pushed
the
ci-pyactions
branch
from
f49470b to
609f3b1
Compare
Codecov Report
@@ Coverage Diff @@
## dev #31 +/- ##
=======================================
Coverage 82.83% 82.83%
=======================================
Files 9 9
Lines 1468 1468
Branches 236 236
=======================================
Hits 1216 1216
Misses 192 192
Partials 60 60
Flags with carried forward coverage won't be shown. Click here to find out more. Continue to review full report at Codecov.
|
umarcor
force-pushed
the
ci-pyactions
branch
2 times, most recently
from
b0eea54 to
1419e65
Compare
umarcor
force-pushed
the
ci-pyactions
branch
from
9bce4e0 to
930f83e
Compare
umarcor
force-pushed
the
ci-pyactions
branch
from
78c125b to
f337716
Compare
umarcor
force-pushed
the
ci-pyactions
branch
3 times, most recently
from
c3f3329 to
1146f38
Compare
umarcor
force-pushed
the
ci-pyactions
branch
from
1146f38 to
d7850ef
Compare
|
pyTooling/Actions#1 is now merged. Do you want to adjust the branch name? I suggest to use a tag like |
See pyTooling/Actions#5. |
|
Ref I think this is ready to review and merge. |
umarcor
force-pushed
the
ci-pyactions
branch
from
9044b45 to
f92fdbb
Compare
In this PR, the CI Pipeline is reworked in order to use reusable workflows from pyTooling/Actions (see pyTooling/Actions#1).
Each job is replaced with a call to a reusable workflow.
As explained in VHDL/pyVHDLModel#36, the logic for dealing with global parameters is changed.
MPORTANT: reusable workflows must be used through an absolute name and specifying a version (see actions/runner#1493). Therefore, this PR will be kept as a draft, because s/@dev/@main/ is required in Pipeline.yml before merging.